Test case to illustrate how to provide input in hexadecimal format for SHA256 gadget, using different settings for bitWidthPerInputElement #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r SHA256 gadget, using different settings for word size
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Ahmed @akosba ,
Thank you for providing a test case at 419907a, illustrating how to use different settings for bitWidthPerInputElement in SHA256 gadget, when inputs are character strings.
Following that example, I have created a test case to illustrate how to provide same input in hexadecimal format, using different setting for bitWidthPerInputElement, which was a use case that I came across. I have built and tested the code. Feel free to add as appropriate.
Thank you.
Best Regards,
Hasini.